Skip to content

logs: Change log-level of output folder destination #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mhovd
Copy link
Collaborator

@mhovd mhovd commented Jul 16, 2025

No description provided.

@Copilot Copilot AI review requested due to automatic review settings July 16, 2025 17:46
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR reduces the verbosity of the log message when writing output files by changing its level from info to debug.

  • Changed the log level for output path messages
  • Ensures quieter default logging during routine output writes
Comments suppressed due to low confidence (2)

src/routines/output.rs:97

  • [nitpick] Consider updating module-level documentation or release notes to reflect that the output path message is now logged at debug level, so users can adjust their log filters accordingly.
            tracing::debug!("Writing outputs to {:?}", self.settings.output().path);

src/routines/output.rs:97

  • [nitpick] Consider adding a unit or integration test to verify that this log message appears at debug level, ensuring the intended log level behavior is maintained.
            tracing::debug!("Writing outputs to {:?}", self.settings.output().path);

Copy link
Contributor

🐰 Bencher Report

Branchlog-level-outputs
Testbedorion
Click to view all benchmark results
BenchmarkLatencyBenchmark Result
seconds (s)
(Result Δ%)
Upper Boundary
seconds (s)
(Limit %)
bimodal_ke_fit📈 view plot
🚷 view threshold
9.82 s
(-34.40%)Baseline: 14.96 s
26.47 s
(37.09%)
🐰 View full continuous benchmarking report in Bencher

@mhovd mhovd requested a review from Siel July 17, 2025 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant